<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" >
	<head>
		<title>iFinity Friendly Url Provider Release Notes</title>
		<style type="text/css">
		    body
		    {
		        font-family:Tahoma;
		        font-size:small;
		    }
		    .note
		    {
		        border:1px dotted;
		        margin:5px; 
		        padding:5px;
		        font-size:smaller;
		    }
		    table
		    {
		        font-family:Tahoma;
		        font-size:small;
		    }
		    th
		    {
		        text-align:left;
		    }
		    td
		    {
		        border:solid;
		    }
		    tr
		    {
		        vertical-align:top;
		    }
		    .imageCont
		    {
		    text-align:center;
		    margin:10px;
		    }
		    .imageTitle
		    {
		    margin-left:20px;
		    margin-right:20px;
		    font-size:smaller;
		    text-align:left;
		    }
		</style>		
	</head>
	<body>
	    <div style="padding:5px;float:right;border:dotted 1px #336699;">
	    <div style="font-weight:bolder;color:#336699;text-align:center;">
	    <img src="ifinity-logo-176-x-57.gif" alt="iFinity Logo"/><br/>
	    iFinity Friendly Url Provider Module</div>
	    <h3>All Help Topics</h3>
	    <ul>
	        <li><a href="UrlRewriting Install Instructions.htm">Install Instructions</a></li>
	        <li><a href="Friendly Url Provider Release Notes.htm">Latest Release Notes</a></li>
	    </ul>
	    </div>
	    <div>
	    
	    <h1>Friendly Url Provider Release Notes</h1>
	    <p>These notes advise on changes to each release.</p>
	    </div>
        <h1>Version 5.4.0 - Released : 25th April 2012</h1>
        <ul>
            <li>Fix for using cached portal aliases</li>
            <li>Fix for Regex patterns to use CultureInvariant for Turkish Language Urls</li>
            <li>Build 5.4.1 - Released 10th May 2012</li>
            <li>652 : 500 Error on DotNetNuke 6 sites</li>
            <li>Build 5.4.3 - Released 20th Sep 2012</li>
            <li>847 : Not redirecting to Url with extension when no-extension Url requested</li>
            <li>848 : Redirect loop on 6.2 popup Urls</li>
        </ul>
        <h1>Version 5.3.0 - Released : 15th April 2011</h1>
        <ul>
            <li>Compatibiltiy with DotNetNuke 5.3</li>
        </ul>
	    <h1>Version 5.1.0 - Released : 14th April 2010</h1>
	    <ul>
	        <li>702 : Object not set error if excluded from secure redirection</li>
	        <li>699 : incorrect encoding on querystring items for diacritic characters</li>
	        <li>717 : when doing 302 redirect for secure connection on home page, don't include /default.aspx</li>
	        <li>727 : stop 301 redirect loop when do301=true included</li>
	        <li>728 : New 'useSiteUrlsRegex' value which forces rewrites to the siteurls.config file</li>
	        <li>730 : Page created via Telerik Control Panel results in 404 because page index not refreshed</li>
	        <li>741 : Standard Url Admin/Host links breaking with IIS7 unless + encoding used</li>
	        <li>749 : Ampersand replacement leaves two characters behind instead of one</li>
	        <li>752 : Original triggerDictionaryRebuildRegex can cause CPU spikes if used with Telerik Control Panel</li>
	        <li>771 : Change duplicate page error to alert instead of exception, improve duplicate page message.</li>
	        <li>776 : Stop exception from occurring when null value saved in permanent redirect Url value.</li>
	        <li>786 : ctl/terms Urls automatically redirected (and /ctl/login, /ctl/register, /ctl/privacy</li>
	        <li>798 : Workaround for NeatUpload component exclusive use of Http Request parameters.</li>
	        <li>809 : replicate DNN Url Rewriter code which starts message processing on application start</li>
	    </ul>
	    <h1>Version 5.0.4 - Released : 1st April 2009</h1>
	    <p>Version 5.0.4 contains some bug fixes found with 5.0.3</p>
	    <h2>Bug Fixes in 5.0.4</h2>
	    <ul>
            <li>usePortalAlias parameter not working (602)</li>
            <li>cannot access settings page for disabled/external pages (594)</li>
	    </ul>	    
	    
        <h1>Version 5.0.3 - Released : 24th February 2009</h1>
	    <p>Version 5.0.3 contains changes to suit dnn 4.9.2/5.0.1</p>
	    <h2>Enhancements in 5.0.3</h2>
	    <ul>
            <li>Support 301 redirects from the DNN Permanent Redirect parameter (588)</li>
	    </ul>	    
	    
        <h1>Version 5.0.2 - Released : 16th February 2009</h1>
	    <p>Version 5.0.2 is a bug fix release</p>
	    <h2>Fixes in 5.0.2</h2>
	    <ul>
            <li>Showing exceptions on 404 errors when running in debug=false mode (588)</li>
            <li>Do not append /default.aspx on subdomain redirection.</li>
	    </ul>	    

        <h1>Version 5.0.1 - Released : 3rd February 2009</h1>
	    <p>Version 5.0.1 is a bug fix release to follow up 5.0.0</p>
	    <h2>Enhancements in 5.0.1</h2>
	    <ul>
            <li>New pages not in cache when created, but cache refreshed after visiting admin->pages (558)</li>
            <li>#anchor urls not redirected correctly when using extensionless urls (575)</li>
	    </ul>	    
	    <h1>Version 5.0.0 - Released : 22nd January 2009</h1>
	    <p>Version 5.0 is compatible with DNN Versions 4.6 upwards, including 5.0 and upwards.</p>
	    <h2>Enhancements in 5.0.0</h2>
	    <ul>
            <li>DNN 5.0 compatibility (553)</li>
	        <li>Change standard settings, including cache rebuild logging, regex exclusions, plus stop redirects for desktopModules and provider paths (560, 545)</li>
	        <li>Can exclude requests for SSL processing with new regex value 'doNotRedirectSecureRegex' (533)</li>
	        <li>New regex pattern for excu</li>
	    </ul>
	    <h2>Bug Fixes in 5.0.0</h2>
	    <ul>
            <li>Disabled tabs to not be logged as duplicates (541).</li>
	        <li>Pages in 'useBaseFriendly' list and are also child pages get 301 redirected, even when 
	        excluded specifically. (549)</li>
	        <li>redirects to subdomains or specified portal aliases append /default.aspx on the end (540)</li>
	        <li>Page cache not refreshed when new page added or name changed (538)</li>
	        <li>Ignore deleted and duplicate pages - do not log in the site log (535)</li>
	        <li>Exclude disabled and duplicate pages - do not log in the site log (534)</li>
	        <li>Ignore CAPTCHA requests using ?alias querystring value (524)</li>
	    </ul>
	    
	    <h1>Version 4.7.1 - Released : 16th October 2008</h1>
	    <p>This release contained minor bugfixes found in the 4.7 release.</p>
	    <ul>
	        <li>allow for domain names which include .aspx as part of the domain. (520)</li>
	    </ul>
	    <h1>Version 4.7.0 - Released : 9th September 2008</h1>
	    <p>Version 4.7 was the rewrite of the provider from the prior 4.6 version.  This included a switch to C# from VB.  
	    Unfortunately change tracking was not enabled prior to this date.</p>
	    
	    <div class="note">
	    Note: Many requests have been received to explain why the cache rebuild message was appearing frequently.  The previous versions used the default DNN cache settings to choose how long to store the information for.  This release implements a new system whereby the administrator can set how long the page index exists in the cache, and whether or not the page index should remain in the cache through an application restart.  However, it is
	    important for people to realise that ultimately it is their web server resources that control how often the cache is flushed.  If the web server is short on resources like memory, it will choose to flush the cache to maintain performance.  Thus, it isn't possible solely through the cache settings to control how often the page index cache gets rebuilt.  A whole-of-server approach needs to be taken.  The messages are now only sent to the application
	    log when the setting is switched on, so most administrators can relax knowing the site log will not fill up.  As long as the site is performing well, there really isn't any great concern about how often the cache is flushed.  To maximise page index build and cache times, reduce the amount of portal alias entries as much as possible, and clean deleted pages out of the recycle bin when they are no longer required.
	    </div>
	</body>
</html>